Initial set of updates to documentation for Stretch#411
Conversation
|
It looks like there's some messed-up formatting which I need to fix: http://ev3dev-lang.readthedocs.io/projects/python-ev3dev/en/stretch-documentation/ If you aren't a maintainer, don't click this link; it isn't complete documentation. |
|
|
||
| Usage Examples | ||
| Usage | ||
| -------------- |
There was a problem hiding this comment.
The underlines should be same length as the titles.
|
|
||
| If you are using a BrickPi, use this line: | ||
| To be able to run your Python file, **your program must be executable**. If | ||
| you're using the `ev3dev Visual Studio Code extension`_, this step will be |
There was a problem hiding this comment.
I think "If you're using the ev3dev Visual Studio Code extension_, you can skip this step, since it will be automatically performed when you download your code to the brick." sounds better. Otherwise it sounds like you can skip this step in any case.
| This little program will run the motor at 500 ticks per second, which on the EV3 | ||
| "large" motors equates to around 1.4 rotations per second, for three seconds | ||
| (3000 milliseconds). | ||
| This will run a LEGO Large Motor at 75% power for 5 rotations. |
|
|
||
|
|
||
| m = LargeMotor(OUTPUT_A) | ||
| m.on_for_rotations(75, 5) |
There was a problem hiding this comment.
This is offtopic, but looking at this line of code I feel it could be more readable. Is 75 here power or rotations? Why the power attribute is on the first place when the method is called on_for_rotations? Why not m.on_for_rotations(5, power=75)?
|
@dwalton76 why's this closed? |
|
@WasabiFan weird it looks like when I deleted |
|
Note: we probably need to add a note somewhere in the Jessie docs to point people to Stretch, and maybe vice versa as well, because web search results might pick up both. |
5431397 to
6e87447
Compare
|
We should figure out how to make the |
| # If true, do not generate a @detailmenu in the "Top" node's menu. | ||
| #texinfo_no_detailmenu = False | ||
|
|
||
| autodoc_member_order = 'bysource' |
There was a problem hiding this comment.
I'd like some feedback on this change. I'm hoping it might make things a bit more logical to sort through... not sure.
There was a problem hiding this comment.
Both bysource (more logical order) and alphabetical (easier to find things) make sense to me. Too bad users can not change this dynamically.
|
The current implementations of the The two solutions I see are:
|
|
@dwalton76 @ddemidov Could I get a review of this? I'd like to see if we can merge this and get a Stretch release out. Question: where should we put info on usage of the new features? A dedicated page just for this version transition? An announcement (ev3dev.org maybe)? A new changelog? Just with each individual class? |
It seemed pretty useless to me given that we have the "tree" immediately above it.
5e89179 to
192df65
Compare
|
Item for discussion: Where do we link to the new upgrading guide? |
9e58bea to
49706b8
Compare
Would a "danger note" somewhere around Getting Started / Usage work? Something like
|
ddemidov
left a comment
There was a problem hiding this comment.
Wow, that is a lot of work! I went though this commit by commit, and it looks good to me. I did not check for completeness (or that the compiled docs actually look good), but I think its better if we merge this and then keep updating the docs as necessary.
|
Thanks for the review! I've merged this and will go update #480 to rebase it on |
|
I'd like to make some more videos for beginners about the VS Code workflow but I don't want to make videos that will quickly be made out of date by the (exciting) introduction of the movetank and movesteering classes. It would be very helpful if you could estimate a date for the initial Stretch release of the Python library. |
|
I intend to release within a day after I merge #480 and #483, which contain important port name updates and some usability improvements for the How about this: If they aren't already merged by mid-day Sunday (my time, PST) I'll merge them anyway 😆 Then I'll test things out to make sure that all of that code works and publish to PyPi. It might take a day or two past that to either figure out how to publish the Debian package myself or get someone else to do it. |
|
I think I still have VM image I used to publish the debian packages, so I could try to make the release when you say it's ready. Although, it may be better if you tried to do it yourself :) |
|
Yeah, I can definitely look into it. I know there's a docs page on it at ev3dev.org (which I might need to adapt for Stretch); the issue is that, once I have built the package, I'll need permissions to actually deploy it anywhere 😆 I'll first just need to get the thing building. |
This is an initial set of documentation updates for Stretch. I rearranged the README so it made a bit more sense to me, added information about the VSCode extension, and added an "upgrading guide".
I'd like a thorough check from others to make sure I didn't do anything stupid
TODOs:
I'm finding it a bit ugly to have to explain adding additional classes to the import list; read it over and tell me what you guys think.
Fixes #399